- 5 minutes to read

How to enable Logging from Ghost Nodes flows to Nodinite

Unlock the power of end-to-end logging for your Ghost Nodes integrations with Nodinite. This guide walks you through enabling and optimizing logging, ensuring you gain full visibility, control, and actionable insights from your integration flows.

✅ Effortless step-by-step setup for Ghost Nodes logging
✅ Centralized monitoring and log management with Nodinite
✅ Flexible log destinations and advanced configuration
✅ Proactive monitoring and alerting for integration health

What is Ghost Nodes? Read more about this innovative new system integrations platform at the Ghost Nodes web site.

graph LR roGNA[fa:fa-ghost Ghost Nodes] --> |Logging| roPS[far:fa-code-commit Nodinite]

Architecture overview: Ghost Nodes sends logging data to Nodinite for centralized monitoring and analysis.

How do I enable logging from Ghost Nodes to Nodinite?

Follow the steps outlined below in order to enable logging from Ghost Nodes to Nodinite.

In this step, you will open a modal in order to manage some logging options.

  • From within the Ghost Studio, first create, or open an existing graph that you want to enable logging for.
  • Then, click on link properties at the top menu.
    Open Link Properties
    Open the link properties in Ghost Studio to access logging options.

In this step, you will set some basic settings to enable logging.

  • Check Enable logging
  • Uncheck Enable summary logs
    Manage Link Properties
    Enable logging and adjust summary log settings as needed.

Step 3: Add log pre-processor

In this step, you will add a Log pre-processor to the graph canvas.

  • Click and drag the Log Pre-processor node onto the graph canvas.
    log pre-processor
    Add the Log Pre-processor node to your Ghost Nodes graph.

  • Select the NodiniteLogEventConverter and click Ok.
    Nodinite Log Event Converter
    Choose NodiniteLogEventConverter to format log events for Nodinite.

Step 4: Manage the NodiniteLogEventConverter

In this step, you will link the NodiniteLogEventConverter with the adapter to receive events to be logged from and set some log-related properties.

  • Connect the logging connector to the adapter you will receive log events from.
    Connect Nodinite Log Event Converter
    Connect the NodiniteLogEventConverter to the appropriate adapter.

  • Click on properties, on the adapter
    Adapter Log Properties
    Access adapter log properties for advanced configuration.

  • Then, on the Advanced tab; Check the checkboxes, depending on what you want to log, and then click Ok.
    Advanced Tab
    Configure advanced logging options for your integration needs.

Step 5: Add and manage the log file destination

In this step, you will manage the destination for the Nodinite JSON Log Events.

  • Drag a Log Destination Node to your graph canvas.
    Add Log Destination
    Add a log destination node to define where logs are stored.

  • Then, select a File Log Destination and click OK.
    File Log Destination
    Choose file log destination for persistent log storage.

Tip

It is possible to use other log destinations. This example uses the file destination node. Review the Nodinite Pickup Service to select the best option for your business case.

  • Connect (or dock), the Nodinite log preprocessor to the log adapter.
    Dock
    Dock the log preprocessor to the log adapter for seamless event flow.

  • Click the exclamation mark in the log adapter to complete the missing path.
    Path
    Set the correct file path for log output.

Note

Make sure the target folder is a highly available file share, otherwise you should log to a share that is local to the node where this graph runs. You do not want to get any problems due to problems with logging.

  • Click the Advanced tab before closing the dialogue, and change the Format when delivering messages to Adapter String Message.
    Advanced file properties
    Set the message format for log delivery.

  • Before deploying, check the mandatory properties of the NodiniteLogEventConverter and change the properties according to your preferences.
    Mandatory Properties
    Review and set mandatory log event properties for Nodinite compatibility.

The properties to be specified match 1:1 with the properties of a Nodinite JSON Log Event.

Mandatory Data Type Field Value Comment
number Log Agent Value Id 6 Log Agent source, who sent the data? This value should rarely change between different graphs
string Original Message TypeName https://nodinite.com/Customers/1.0#Batch Message Type Name
number LogEvent Endpoint Type Ghost Nodes Select the type of Endpoint transport
bool Use UTC timestamps Checked/Unchecked Use datetime in ISO8601 format or use the local time
number LogEvent Event Direction 0 Select the type of Direction for the Endpoint transport
string ApplicationInterchangeId "" Id for Application scope, use to keep related events together

Step 6: Deploy

In this step, the design phase in Ghost Nodes is over, and you can soon enjoy the logged result from within the Nodinite Web Client using one or more self-service enable Log Views.

If you need logging from other adapters, repeat the steps as necessary by your requirements and specifications.

  • Press Deploy to start the node sending logs, exceptions and payloads to Nodinite.
    Deploy
    Deploy your Ghost Nodes graph to activate logging to Nodinite.

Step 7: Configure Nodinite Pickup Service

The output log files must now be consumed by the Nodinite Pickup Service.

  • Install

  • Configure

  • You should monitor the shares/folders with output files from Ghost Nodes. Use the Nodinite File Monitoring Agent.

  • You can create monitoring to give you alerts for missing log events or when content does not conform to your standards. Use the Nodinite Non-Events Monitoring Agent.

  • You can probably use many other Nodinite Monitoring Agents to make sure every node and dependent resources in a Ghost Nodes installation, is healthy.

Next Step

Add or Manage Log Views

Log Views
Asynchronous Logging